X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86452.8F73CEC5@onstor-exch02.onstor.net>; Thu, 31 Jan 2008 13:45:13 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86452.8F73CEC5"
Content-class: urn:content-classes:message
Subject: RE: Functional specification for DameWare & Security Explorer Support
Date: Thu, 31 Jan 2008 13:45:13 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08058B44@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E07FB5835@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Functional specification for DameWare & Security Explorer Support
Thread-Index: AcheGbb1QsTDKwOQQ1yaSh0HZm5nqwD+r6zAACjbpfAAZWzHoA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E07D4F2D1@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E07FB51D4@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E07FB5835@onstor-exch02.onstor.net>
From: "Ron Bhanukitsiri" <ronb@onstor.com>
To: "Allan Burrington" <allan.burrington@onstor.com>,
	"Dave Limato" <dave.limato@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	"Joshua Goldenhar" <joshua.goldenhar@onstor.com>,
	"Brian Montero" <brian.montero@onstor.com>,
	"Steffen Thuemmel" <steffen.thuemmel@onstor.com>,
	"Narayan Venkat" <narayan.venkat@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86452.8F73CEC5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for your valuable feedback, Allan.

Indeed, returning domain users and groups can be convincing.  At this
time,
Jonathan and I feel that we should keep things the way they were.  Also,
the product has always returned domain and local users when using MMC
and apparently customers seem ok with this.  However, we do plan to
document the difference.

Ron B[ee]

_____________________________________________
From: Allan Burrington=20
Sent: Tuesday, January 29, 2008 1:44 PM
To: Dave Limato; Ron Bhanukitsiri; dl-Design Review; dl-QA; Joshua
Goldenhar; Brian Montero; Steffen Thuemmel; Narayan Venkat
Subject: RE: Functional specification for DameWare & Security Explorer
Support

Regarding what should be sent back for users/groups...

In Computer Manager, users/groups are explicitly 'local' in reference to
the target you're managing.  It's not a pass-through operation to the
domain that target is a member of.  To manage those users, you would go
to the DC or the AD for that domain.  With DameWare (or other integrated
management interfaces) it's going to make life very confusing for the
operator if the filer is returning users that can't be managed through
the filer.

When a client queries the local users on a Windows box, it sends across:
	SamrConnect5 to the host - connect to the machine's sam database
	SamrEnumerateDomainsInSamServer, response:  <localName>, Builtin
	SamrLookupDomainsInSamServer <localName>, response
SID:<machinesid>
	SamrOpenDomain, <machinesid>
	SamrQueryDisplayInformation level 1 - to iterate through the
members of <localsid>

When a client queries the local users on the filer, the dialog is:
	SamrConnect4 to the host
	SamrEnumerateDomainsInSamServer <localname>, response: MATRIX,
Builtin
The problem here is that the client now opens the Matrix domain and
iterates through its users.

The windows boxes do not respond with their domain membership, their
responses are from their local sam database.=20

If we don't have a local sam database, then either remove the localname
from the EnumerateDomainsInSamServer response, or respond with the
machine's sid and then return an empty list to QueryDisplayInformation.=20

-A

_____________________________________________
From: Dave Limato=20
Sent: Monday, January 28, 2008 5:27 PM
To: Ron Bhanukitsiri; dl-Design Review; dl-QA; Joshua Goldenhar; Brian
Montero; Steffen Thuemmel; Narayan Venkat
Subject: RE: Functional specification for DameWare & Security Explorer
Support


Regarding the TBD list. Has any progress been made by this. Specifically
Search and Users?=20

Features TBD:
*	Disk Drives - filer does not support DOS drive letters (C:, D:,
etc.).  The Win32 API (i.e. NetDiskEnum RPC) does not have support for
volumes.
*	Search - share search should work.  User search returns domain
user.  Global and Local Group search does not work (does not work with
Windows server as well)
*	Users - filer currently returns list of domain users since we do
not have local users
*	Groups - filer currently returns list of domain groups since we
do not have local groups

Or are we just sticking with the "to be supported" list?=20

Regarding the Users Groups recommendation on the end of Page 25, I
agree, we should only report what our NAS reports, domain users and
groups.
Also, thanks for the Testing Strategy Tips!
Cheers! Dave
_____________________________________________
From: Ron Bhanukitsiri=20
Sent: Wednesday, January 23, 2008 3:43 PM
To: dl-Design Review; dl-QA; Joshua Goldenhar; Brian Montero; Dave
Limato; Steffen Thuemmel; Narayan Venkat
Subject: Functional specification for DameWare & Security Explorer
Support

Dear Esteemed Colleagues,

Here's the first cut of the functional spec.  Comments are warmly
welcome.

Thanks,
Ron B[ee]

 << File: DameWare & Security Explorer Support FuncSpec.doc >>=20

------_=_NextPart_001_01C86452.8F73CEC5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Functional specification for DameWare &amp; Security Explorer =
Support</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial">for your valuable feedback, =
Allan.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Indeed, returning domain users and groups can be =
convincing.&nbsp; At this time,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Jonathan and I feel that we =
should keep things the way they were.&nbsp; Also,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">the product has always returned domain and local users =
when</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">using</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" =
SIZE=3D2 FACE=3D"Arial"> MMC</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">and apparently customers seem ok with =
this.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">&nbsp; =
However, we do plan to</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">document the difference.</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Ron B[ee]</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Allan Burrington<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, January 29, 2008 =
1:44 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Dave Limato; Ron =
Bhanukitsiri; dl-Design Review; dl-QA; Joshua Goldenhar; Brian Montero; =
Steffen Thuemmel; Narayan Venkat<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Functional specification for DameWare &amp; =
Security Explorer Support</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">Regarding what should be sent back =
for users/groups&#8230;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">In Computer Manager, users/groups are explicitly =
&#8216;local&#8217; in reference to the target you&#8217;re =
managing.&nbsp; It&#8217;s not a pass-through operation to the domain =
that target is a member of.&nbsp; To manage those users, you would go to =
the DC or the AD for that domain.&nbsp; With DameWare (or other =
integrated management interfaces) it&#8217;s going to make life very =
confusing for the operator if the filer is returning users that =
can&#8217;t be managed through the filer.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">When a client queries the local users on a Windows box, =
it sends across:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrConnect5 to the host &#8211; =
connect to the machine&#8217;s sam database</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrEnumerateDomainsInSamServer, =
response:&nbsp; &lt;localName&gt;, Builtin</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrLookupDomainsInSamServer =
&lt;localName&gt;, response SID:&lt;machinesid&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrOpenDomain, =
&lt;machinesid&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrQueryDisplayInformation level 1 =
&#8211; to iterate through the members of =
&lt;localsid&gt;</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">When a client queries the local users on the filer, the =
dialog is:</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrConnect4 to the =
host</FONT></SPAN></P>

<P DIR=3DLTR><SPAN =
LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
COLOR=3D"#1F497D" FACE=3D"Calibri">SamrEnumerateDomainsInSamServer =
&lt;localname&gt;, response: MATRIX, Builtin</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">The problem here is that the client now opens the =
Matrix domain and iterates through its users.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">The windows boxes do not respond with their domain =
membership, their responses are from their local sam database. =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">If we don&#8217;t have a local sam database, then =
either remove the localname from the EnumerateDomainsInSamServer =
response, or respond with the machine&#8217;s sid and then return an =
empty list to QueryDisplayInformation. </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#1F497D" =
FACE=3D"Calibri">-A</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Dave Limato<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Monday, January 28, 2008 =
5:27 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Ron Bhanukitsiri; =
dl-Design Review; dl-QA; Joshua Goldenhar; Brian Montero; Steffen =
Thuemmel; Narayan Venkat<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> RE: Functional specification for DameWare &amp; =
Security Explorer Support</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Regarding the TBD list. Has =
any progress been made by this. Specifically Search and Users? =
</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B>Features TBD:</B></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Symbol">&#183;<FONT =
FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"><B></B> Disk Drives &#8211; filer does not support DOS =
drive letters (C:, D:, etc.).&nbsp; The Win32 API (i.e. NetDiskEnum RPC) =
does not have support for volumes.</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Symbol">&#183;<FONT =
FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"> Search &#8211; share search should work.&nbsp; User =
search returns domain user.&nbsp; Global and Local Group search does not =
work (does not work with Windows server as well)</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Symbol">&#183;<FONT =
FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"> Users &#8211; filer currently returns list of<I> =
domain</I> users since we do not have local users</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT FACE=3D"Symbol">&#183;<FONT =
FACE=3D"Courier =
New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></FONT></SPAN><SPAN =
LANG=3D"en-us"> Groups &#8211; filer currently returns list of<I> =
domain</I> groups since we do not have local groups</SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Or are we just sticking with =
the &#8220;to be supported&#8221; list? </FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Regarding the Users Groups =
recommendation on the end of Page 25, I agree, we should only report =
what our NAS reports, domain users and groups.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Also, thanks for the Testing =
Strategy Tips!</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Cheers! Dave</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Ron Bhanukitsiri<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Wednesday, January 23, =
2008 3:43 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Design Review; dl-QA; =
Joshua Goldenhar; Brian Montero; Dave Limato; Steffen Thuemmel; Narayan =
Venkat<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Functional specification for DameWare &amp; Security =
Explorer Support</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">Dear Esteemed Colleagues,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Here&#8217;s the first cut of the functional spec.&nbsp; =
Comments are warmly welcome.</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Ron =
B[ee]</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us">&nbsp;&lt;&lt; File: DameWare &amp; =
Security Explorer Support FuncSpec.doc &gt;&gt;</SPAN><SPAN =
LANG=3D"en-us"> </SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C86452.8F73CEC5--
